home *** CD-ROM | disk | FTP | other *** search
- Path: news.axess.com!usenet
- From: exact@axess.com (Kamikaze)
- Newsgroups: alt.winsock.programming,comp.lang.c++,comp.os.ms-windows.networking.tcp-ip
- Subject: Why is Novell TCP/IP not working?
- Date: Fri, 12 Jan 1996 12:49:38 GMT
- Organization: Axess Communications
- Message-ID: <4d5au8$qs5@news.axess.com>
- NNTP-Posting-Host: cretien.axess.com
- X-Newsreader: Forte Free Agent v0.55
-
- Hi
-
- I wonder if anyone out there has experienced this phenomenon with
- their Novell Lan WorkPlace Windows Sockets API v1.1?
-
- I'm trying to write a server application, I'm able to intitiate a
- WSAStartup(), make a socket, bind it but as soon as I call
- WSAAsynchSelect() I get a ENETDOWN error. I've tried using a utility
- called Windows Socket Test and it gives me the same result. I have
- tried the same program and Socket test program on my solitary computer
- at home using Trumpet winsock and everything is fine, which leads me
- to conclude that Novell may be the culprit.
-
- I have recently read of a few posts in the compuserve forums detailing
- the same problem. If I didn't know better the asynchrous functions
- don't seem to work. Could this be true and if so is there a patch I
- can use?
-
- Any help with this mysterious case would be greatly appreciated.
-
- Thanks,
-
-
- Bishop Arabesque Terry Drymonacos
- Church of Latter Day Taoists exact@cam.org
- Mediocrity is our only enemy. aka Kamikaze
-
-